|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Proposed Standard
|
|
3.
|
Justification for the specific reference:
|
|
|
This Recommendation makes reference to the IP Security Protocol (IPsec), its architecture is defined in IETF RFC 4301.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
None.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since December 2005. It is updated by RFC 6040 and RFC 7619. It obsoletes RFC 2401 and updates RFC 3168.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 4301 has been in existence for nearly 10 years. IPSec is widely used in the internet.Errata exists. Obsoletes RFC 2401. Updates RFC 3168
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 4301 defines the architecture of the IPsec protocols.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[BBCDWW98] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z., and W. Weiss, "An Architecture for Differentiated Service", RFC 2475, December 1998./
[Bra97] Bradner, S., "Key words for use in RFCs to Indicate Requirement Level", BCP 14, RFC 2119, March 1997./
[CD98] Conta, A. and S. Deering, "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification", RFC 2463, December 1998./
[DH98] Deering, S., and R. Hinden, "Internet Protocol,Version 6 (IPv6) Specification", RFC 2460, December 1998./
[Eas05] 3rd Eastlake, D., "Cryptographic Algorithm Implementation Requirements For Encapsulating Security Payload (ESP) and Authentication Header (AH)", RFC 4305, December 2005./
[HarCar98] Harkins, D. and D. Carrel, "The Internet Key Exchange (IKE)", RFC 2409, November 1998./
[Kau05] Kaufman, C., Ed., "The Internet Key Exchange (IKEv2) Protocol", RFC 4306, December 2005./
[Ken05a] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303, December 2005./
[Ken05b] Kent, S., "IP Authentication Header", RFC 4302, December 2005./
[MD90] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191, November 1990./
[Mobip] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004./
[Pos81a] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981./
[Pos81b] Postel, J., "Internet Control Message Protocol", RFC 792, September 1981./
[Sch05] Schiller, J., "Cryptographic Algorithms for use in the Internet Key Exchange Version 2 (IKEv2)", RFC 4307, December 2005./
[WaKiHo97] Wahl, M., Kille, S., and T. Howes, "Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names", RFC 2253, December 1997./
/
Informative References/
/
[CoSa04] Condell, M., and L. Sanchez, "On the Deterministic Enforcement of Un-ordered Security Policies", BBN Technical Memo 1346, March 2004./
[FaLiHaMeTr00] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P.Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, March 2000./
[Gro02] Grossman, D., "New Terminology and Clarifications for Diffserv", RFC 3260, April 2002./
[HC03] Holbrook, H. and B. Cain, "Source Specific Multicast for IP", Work in Progress, November 3, 2002./
[HA94] Haller, N. and R. Atkinson, "On Internet Authentication", RFC 1704, October 1994./
[NiBlBaBL98] Nichols, K., Blake, S., Baker, F., and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998./
[Per96] Perkins, C., "IP Encapsulation within IP", RFC 2003, October 1996./
[RaFlBl01] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition of Explicit Congestion Notification (ECN) to IP", RFC 3168, September 2001./
[RFC2401] Kent, S. and R. Atkinson, "Security Architecture for the Internet Protocol", RFC 2401, November 1998./
[RFC2983] Black, D., "Differentiated Services and Tunnels", RFC 2983, October 2000./
[RFC3547] Baugher, M., Weis, B., Hardjono, T., and H. Harney, "The Group Domain of Interpretation", RFC 3547, July 2003./
[RFC3740] Hardjono, T. and B. Weis, "The Multicast Group Security Architecture", RFC 3740, March 2004./
[RaCoCaDe04] Rajahalme, J., Conta, A., Carpenter, B., and S.Deering, "IPv6 Flow Label Specification", RFC 3697, March 2004./
[Sch94] Schneier, B., Applied Cryptography, Section 8.6, John Wiley & Sons, New York, NY, 1994./
[Shi00] Shirey, R., "Internet Security Glossary", RFC 2828, May 2000./
[SMPT01] Shacham, A., Monsour, B., Pereira, R., and M. Thomas, "IP Payload Compression Protocol (IPComp)", RFC 3173, September 2001./
[ToEgWa04] Touch, J., Eggert, L., and Y. Wang, "Use of IPsec Transport Mode for Dynamic Routing", RFC 3884, September 2004./
[VK83] V.L. Voydock & S.T. Kent, "Security Mechanisms in High-level Networks", ACM Computing Surveys, Vol. 15, No. 2, June 1983.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
|
